Test this pull request

• The @dcl/protocol package can be tested in scenes by running

  npm install "https://sdk-team-cdn.decentraland.org/@dcl/protocol/branch//dcl-protocol-1.0.0-33676973640.commit-0c3d984.tgz"

On the red "Validate compatibility with main branch" check: it flags world_coordinates moving "from outside to inside a oneof" because proto3 optional puts the field in a synthetic oneof in the descriptor. For a message-typed field that changes nothing on the wire or in JSON. Message fields already have explicit presence in proto3: set → written as tag 1, length-delimited; unset → omitted. Before and after this change a serializer produces byte-identical output, and the generated TypeScript only widens (worldCoordinates: Vector2 | undefined → worldCoordinates?: Vector2 | undefined). (For a scalar field optional would change presence semantics, which is what the rule is really guarding.)

So against main, which has neither field, the whole change is additive:

• an older scene always sets world_coordinates, and a newer client reads it exactly as before; realm is simply absent.
• a newer scene that sets a parcel sends the bytes older clients already parse; one that sets only realm sends an unknown field 2 (skipped) and no field 1, which decodes fine and degrades to that client's handling of a parcel-less teleport.

The flag itself is a tooling artifact of the pinned buf version. With the repo's own WIRE_JSON config, this branch against main:

Newer buf recognises the synthetic oneof of a proto3 optional field. Bumping the pinned version would clear the check without touching the rules; otherwise the block can be bypassed for this PR on the grounds above.